To configure a Generic QoS Profile

Purpose

The Generic QoS Profile (GQP) provides an abstraction layer above the specific 7x50, 7210, and Multi Vendor QoS policies in the NFM-P. This functionality allows users to create QoS profiles that are generic for both proprietary NEs and third party NEs.

Note: Considerations for binding policies to GQPs

The following considerations apply when binding SAP Access Ingress/Egress policies or 7210 SAP Access Ingress/Egress policies to the GQP:

When applying a SAP Access Ingress/Egress policy or 7210 SAP Access Ingress/Egress policy to the GQP, you can only apply those policies that have matching queues/meters/policers with the GQPs.
Upon GQP creation and when the relevant GQP properties are left empty, relevant values from the assigned ingress policy and/or the egress policy are used to auto-populate the relevant GQP properties. This only occurs upon GQP creation and only if a policy is added. If any of the GQP properties are edited, this will not occur. Additional policies can be added after initial creation. The relevant properties are those set in the policy’s queues, meters and policers.
During the auto-populate, if a policy has the same queue ID entry as a policer/meter entry and the same CIR, PIR, CBS, or MBS characteristics, the ingress buffers are auto-populated, displaying the type as Not Applicable in the GQP. When the entries have different CIR, PIR, CBS, or MBS characteristics, the ingress buffers are auto-populated, displaying the type as Queue in the GQP.
When comparing queue/meter/policers entries between the two policy types: only the first 8 queue entries are used for comparison; for meter and policer entries, only the first 32 entries are used.
When you select an additional ingress or egress policy after the first ingress or egress policy has been selected, only policies with matching relevant properties are displayed in the select NFM-P window.
When a GQP is cloned or modified using an API, the NFM-P creates a corresponding GQP and related ingress and egress QoS policies.

Steps


1	Choose Policies→QoS→Generic QoS Profiles from the NFM-P main menu. The Generic QoS Profiles form opens.
2	Click Create or choose a Generic QoS Profile and click Properties. The Generic QoS Profile (Create \| Edit) form opens.
3	Configure the required parameters on the General tab. If the MultiVendor Policies parameter is enabled, and the Generic QoS Profile is being created or modified, all appropriate multi-vendor global policies are auto-generated upon applying the change. The multi-vendor policies are automatically added to the GQP, but do not replace any non-auto-generated policies which are already there. You can view the generated policies on the QoS Policies tab of the GQP and in the policy managers from the NFM-P main menu, Policies→Multi-Vendor, after the GQP changes are applied. In a similar way to the auto-population of GQP values, the NFM-P extracts the values set in the GQP buffer (of type Policer only), Class of Service, and Match Criteria, and auto-generates Multi-Vendor QoS policies to match these properties. The new policies are created with a fixed naming convention, ending with a number. Upon creation of these new policies, if the NFM-P finds an existing policy with the same name and number, it checks if any local definitions of that policy (or any component policies already bound to that policy) exist. If there are no local definitions, the NFM-P updates the existing policies and ensures they are assigned to the GQP. If a local definition does exist, the NFM-P creates a new set of policies with the same names as the existing policies, but with incremental numbers. The original policies in the GQP are then replaced with new policies. This is done to ensure that policy distribution to the NEs is as accurate as possible. The set of attributes which are supported by the auto-generation are described in the NSP NFM-P Multi-Vendor Policy Guide.
4	Configure an Egress QoS Buffer, Class of Service, Match Criteria, and Scheduling. Click on the Egress tab, then the Buffer sub-tab. Click Create or select an existing buffer and click Properties. The Egress QoS Buffer form opens. Configure the required parameters. The Buffer ID is mandatory and can represent a queue, policer, or meter. Note: When a generic QoS profile contains a buffer with its Buffer Type set to N/A, then based on Buffer ID matching, both the queue and policer entries are updated in the policy. However, if the Buffer Type is configured as Policer, then only the corresponding policer that matches the Buffer ID is overridden in the policy. If the Buffer Type is configured as Queue, then only the corresponding queue that matches the Buffer ID is overridden in the policy. Click OK to save the changes and close the form. Click on the Class of Services sub-tab. Select one of the eight default Class Names and click Properties. The Egress QoS Class of Service form opens. Configure the Description parameter and select a Buffer ID to associate with this Class Name. Click OK to save the changes and close the form. Click on the Match Criteria sub-tab. Click Create or select an existing entry and click Properties. The Egress QoS Match Criteria form opens. Configure the parameters on the General tab. Configure the parameters on the IPv4 Match Criteria, IPv6 Match Criteria, and MAC Match Criteria tabs, as required. Click OK to save the changes and close the form. Click on the Scheduling sub-tab. Click Create or select an existing QoS Scheduler and click Properties. The Egress QoS Scheduler form opens. Configure the Name parameter and select a scheduler Type, then configure the remaining parameters. Click OK to save the changes and close the form. Repeat substeps 2 to 17 to configure additional egress buffers.
5	Configure an Ingress QoS Buffer, Class of Service, Match Criteria, and Scheduling. Click on the Ingress tab, then the Buffer sub-tab. Click Create or select an existing buffer and click Properties. The Ingress QoS Buffer form opens. Configure the required parameters. The Buffer ID is mandatory and can represent a queue, policer, or meter. Note: When a generic QoS profile contains a buffer with its Buffer Type set to N/A, then based on Buffer ID matching, both the queue and policer entries are updated in the policy. However, if the Buffer Type is configured as Policer, then only the corresponding policer that matches the Buffer ID would be overridden in the policy. If the Buffer Type is configured as Queue, then only the corresponding queue that matches the Buffer ID would be overridden in the policy. Click OK to save the changes and close the form. Click on the Class of Services sub-tab. Select one of the eight default Class Names and click Properties. The Ingress QoS Class of Service form opens. Configure the Description parameter and select a Buffer ID to associate with this Class Name. Click OK to save the changes and close the form. Click on the Match Criteria sub-tab. Click Create or select an existing entry and click Properties. The Ingress QoS Match Criteria form opens. Configure the parameters on the General tab. Configure the parameters on the IPv4 Match Criteria, IPv6 Match Criteria, and MAC Match Criteria tabs, as required. Click OK to save the changes and close the form. Click on the Scheduling sub-tab. Click Create or select an existing QoS Scheduler and click Properties. The Ingress QoS Scheduler form opens. Configure the Name parameter and select a scheduler Type, then configure the remaining parameters. Click OK to save the changes and close the form. Repeat substeps 2 to 17 to configure additional ingress buffers.
6	Assign QoS policies to the profile. Perform one of the following: For Nokia equipment: Click on the QoS Policies tab. For an SROS NE, click the SROS Ingress/Egress sub-tab and then click the appropriate Select buttons to choose the required QoS policies. The policy types include: SAP Access Ingress Policy SAP Access Egress Policy Ingress Scheduler Policy Egress Scheduler Policy Ingress Policer Control Policy Egress Policer Control Policy For a 7210 NE, click the 7210 Ingress/Egress sub-tab and then click the appropriate Select buttons to choose the required QoS policies. The policy types include: 7210 SAP Access Ingress Policy 7210 SAP Access Egress Policy For multi-vendor equipment: Click on the QoS Policies tab, then the Multi Vendor Ingress/Egress Policies sub-tab. Click the appropriate sub-tab to choose the required policies. The policy types include: QoS Policies Policers Filters Generic Policies Click Add, then choose a policy from the Select form. Click OK to close the form.
7	If you are viewing or configuring an existing Generic QoS Profile, you can click on the Dynamic Policies tab to view a list of dynamic policies associated with this profile. Such a policy is a local definition automatically created by the NFM-P when it receives a QoS policy override request from NSP. Dynamic policies are essentially cloned SAP ingress or egress QoS policies that are used to override the CIR, PIR, CBS, and/or MBS values of the queues (and additionally, set policer overrides on 7x50 NEs). These policies are then deployed to specific NEs for service application. The Generic QoS Profile functionality is used to accomplish this. Dynamic policies are not listed in the standard QoS policy forms, since they are not created from the NFM-P or through CLI or the XML API. You can only view dynamic policies and their implicit association to service SAPs, shown on the Access interfaces tab and its sub-tabs. A dynamic policy will automatically be removed from this list under the following conditions: the related service is deleted the related service SAP is deleted the QoS policy is cleared on the related service SAP the daughter card containing the service SAP port is removed Dynamic policies are Local Edit Only policies that do not have any global reference. In addition, all local access ingress and egress policies contain a read-only attribute named Policy Mode that indicates if a policy is Dynamic or Static. In this context, Dynamic means the values have been modified by the Generic QoS Profile. This also includes policies for 7210 SAS variants where override support is not present by default.
8	Click OK to save the profile and close the form. End of steps