global-res-profile
config>system
7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-Sx/S 1/10GE: standalone
Commands in this context configure the CAM resources.
enable-bgp-3107-frr
no enable-bgp3107-frr
config>system>global-res-profile
7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-Sx/S 1/10GE (standalone-VC)
This command enables the allocation of MPLS FIB and protection group resources required for enabling uniform 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>global-res-profile
7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-Sx/S 1/10GE (standalone-VC)
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
qos
config>system>glob-res-profile
7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-Sx/S 1/10GE: standalone
Commands in this context configure the QoS resources.
no port-scheduler-mode
port-scheduler-mode
config>system>glob-res-profile
7210 SAS-R6 and 7210 SAS-R12 (supported only on IMMv2 cards)
This command lets user select 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.
When port-scheduler-mode is disabled using the no form of this command, per SAP egress queues are 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
sf-ingress-internal-tcam
config>system>glob-res-profile
7210 SAS-R6 and 7210 SAS-R12
Commands in this context configure the CAM resources available in the SF/CPM.
The sf-ingress-internal-tcam resource pool is shared by multiple features. The resources are allocated in chunks of fixed size. 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 for the feature. Resources are allocated to features in chunks of fixed size. It is not possible to for a chunk to be shared by multiple features. There are a few exceptions which are specified explicitly. The 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, user can allocate more chunks to the feature (by taking away chunks of resources from other features which do not need to be enabled).
To free up the resources for use by other features, 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 UP MEPs and allocate it to P2MP LSPs, user will need to remove the configuration of UP MEPs for all the SAPs, then change the resource profile configuration to allocate the chunk to P2MP LSPs. Another scenario would be, to free up a chunk of resources and allocate it to another feature.
The sf-ingress-internal-tcam resource pool is shared among the following features on different platforms:
7210 SAS-R6 and 7210 SAS-R12
It is global per node resource pool. It is shared among UP MEPs, G8032 Fast-flood, and NG-MVPN P2MP LSPs.
While reassigning chunk of resources among features, in some scenarios a reboot of the node might be required. See the CLI description of the specific feature to know more.
The number of chunks and the number of resources per chunk varies among the different platforms. Contact your ALU/Nokia representative for more information.
On 7210 SAS-R6, the number of resources per slice/chunk varies. Hence, the number of resources allocated to a feature varies based on the order of allocation of resources among the different features. It might be necessary to allocate more slices to a feature to achieve desired scaling.
For some features a minimum number of chunks (greater than 1) must be allocated to enable the feature functionality. If this is not done software cannot allocate the required number of resources and it will fail the command associated with the feature.
eth-cfm-upmeps max_slices
no eth-cfm-upmeps
config>system>glob-res-profile>sf-ingress-internal-tcam
7210 SAS-R6 and 7210 SAS-R12
This command allocates resources towards UP MEP from the sf-ingress-internal-tcam pool. The value specified here allocates a fixed number of entries for use with this feature. Entries are allocated by software from this pool whenever UP MEP is configured in a VPLS service (either on a SAP or a SDP). The number of entries required per MEP depends on the level of the MEP.
The no form of this command 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.
Specifies the number of slice to be allocated for VPLS UP MEP feature. Each slice has many resource entries which is used to identify and process VPLS UP MEP messages.
g8032-fast-flood max_slices
no g8032-fast-flood
config>system>glob-res-profile>sf-ingress-internal-tcam
7210 SAS-R6 and 7210 SAS-R12
This command configures the amount of ingress internal CAM resources available in the SF/CPM for use by G8032 fast-flood mechanism. These are used to implement G8032 fast-flood for data services protected using G8032 ring protection mechanism. The amount of slices determines the amount of data services that can be protected by G8032 and use the fast-flood mechanism to reduce the convergence time on a ring failure and switchover.
On IMMv2, resources are used to implement the G8032 fast-flood mechanism for only RVPLS services. These resources are used only if G8032 is enabled for RVPLS services. The G8032 fast-flood mechanism is also implemented for VPLS services, but no user configuration is required and it does not need resources to be allocated from the sf-ingress-internal-tcam pool.
Specifies the number of slices to be allocated for the G8032 fast-flood mechanism. Each slice has many resource entries that are used to implement G8032 fast flood for multiple data services protected by G8032.
mpls-p2mp max_slices
no mpls-p2mp
config>system>glob-res-profile>sf-ingress-internal-tcam
7210 SAS-R6 and 7210 SAS-R12
This command allows the user to configure the resources to be used for NG-MVPN P2MP LSPs. The users must allocate some resources using the command before configuring NG-MVPN. It might be necessary to free up resources allocated to other features to allocate resources for it.
On 7210 SAS-R6, the number of resources per slice/chunk varies. Hence, the number of resources allocated to a feature varies based on the order of allocation of resources among different features. It might be necessary to allocate more slices to a feature to achieve desired scaling.
The no form of this command does not allocate any resources for use by P2MP LSPs used with NG-MVPN feature. If no resources are allocated for use, the software will not be able to setup P2MP LSPs for use with NG-MVPN.
Specifies the number of slices to be allocated for NG-MVPN P2MP LSPs.