NSP Network Services Platform Network Functions Manager - Packet (NFM-P) Multi-Vendor Policy Guide. 3HE AAAB-TQZZA Issue 2 September 2017

Transcription

1 NSP Network Services Platform Network Functions Manager - Packet (NFM-P) Multi-Vendor Policy Guide 3HE AAAB-TQZZA

2 Legal notice Nokia is a registered trademark of Nokia Corporation. Other products and company names mentioned herein may be trademarks or tradenames of their respective owners. The information presented is subject to change without notice. No responsibility is assumed for inaccuracies contained herein Nokia. 2 3HE AAAB-TQZZA

3 Contents About this document...4 Multi-Vendor Policy Guide To configure a multi-vendor filter policy To configure a multi-vendor policer policy To configure a multi-vendor forwarding class policy To configure a multi-vendor class matching policy To configure a multi-vendor QoS policy To view multi-vendor generic policies QoS Code Point Values HE AAAB-TQZZA 3

4 About this document Purpose Overview The NFM-P supports the configuration of policies for multi-vendor devices using drivers. Driver modules are capable of translating the device-independent NFM-P configuration to device-specific configuration. The device-independent NFM-P multi-vendor policy configuration procedures are described in this document. This document is intended for NFM-P users configuring policies and for driver developers who provide the mapping of device-specific values to NFM-P values. Released policies can be distributed in bulk to specified NEs. You can monitor, change, and manage changes via local and global policies. You can also perform policy audits to identify the differences between local and global policies. When discrepancies are identified, you can synchronize the policies. Configuration of multi-vendor policies includes: packet filtering and classification policing shaping metering queue definitions scheduler definitions class definitions Multi-vendor policy attributes The multi-vendor policy model in the NFM-P extensively uses string list attributes for policy conditions and actions. The NFM-P device-independent values of these conditions and actions are listed in this document. It is important to note that the standard attribute values are device-independent. However, there may be a situation when device-specific values are required. To add flexibility, the NFM-P allows vendor- or device-specific conditions or actions to be deployed and resynchronized, if the corresponding vendor's driver supports these non-standard translations. To deploy these conditions or actions, certain syntax- appending a - at the front of each condition or action, is recommended. This can be extended by adding the vendor name to the special character. This is required to avoid conflicts with other non-standard values from different vendors that may become standard in the future. For example, the following is a standard condition to match the DSCP value in a filter: match dscp af12 A non-standard value to match a different condition would be: -cisco-match cos 2 4 3HE AAAB-TQZZA

5 In this example, the specific value begins with a "-" followed by the vendor name, the full prefix is "-cisco-" and the actual condition is "match cos 2". Non-standard (driver/node-specific) attributes are listed in the driver documentation if available. Generic QoS profile and auto-generated multi-vendor policies During the creation of a GQP, if the MultiVendor Policies parameter is enabled, all appropriate multivendor global policies are auto-generated upon applying the change. These multi-vendor policies are automatically added to the GQP, but do not replace any non-auto-generated policies which are already there. The generated multi-vendor policies cannot be deleted when they are associated with a GQP. If the generated policies are edited, the changes may impact the intended functionality of the GQP. The generated policies should only be assigned through the use of the GQP functionality. The new policies are created with a fixed naming convention, ending with a number: <gqpname>.<policypurpose>.<version> Example: FilterPolicy - GQP1.in.inet.1 QoSPolicy - GQP2.out.5 For more information, see To configure a Generic QoS Profile in the NSP NFM-P User Guide. Document support How to comment Customer documentation and product support URLs: Customer Documentation Welcome Page Technical support Documentation feedback 3HE AAAB-TQZZA 5

6 To configure a multi-vendor filter policy NFM-P Multi-Vendor Policy Guide 1 To configure a multi-vendor filter policy 1.1 Steps Choose Policies Multi-Vendor Filter from the NFM-P main menu. The Multi-Vendor Filter Policies form opens. Click Create or choose a multi-vendor filter policy and click Properties. The Multi-Vendor Filter Policy (Create Edit) form opens. Configure the parameters in the Identity panel and click Apply. If required, configure custom properties. 1. Click on the Custom Properties tab and click Add. The Entry Value form opens. 2. Configure the Key and Value parameters and click OK. Repeat this step to configure more custom properties, as required. Click on the Filter Terms tab and click Create. The Multi-Vendor Policy Filter Term (Create) form opens. Configure the Term Name parameter and if required, select a Filter Policy. Click on the Filter Conditions tab and click Add. The Entry Value form opens. Configure the Value parameter and click OK. Values of the string list (property genericne.filterterm.conditionlist) are the supported conditions to perform packet classification and/or and filtering. 6 3HE AAAB-TQZZA

7 To configure a multi-vendor filter policy Table 1 NFM-P Filter Policy supported conditions Condition Description IPv4 and IPv6 Filter conditions match except dscp value match except prec value match except protocol value match except ip-addr address match except port number match except src-ip-addr address src-port number match except dst-ip-addr address match except dst-port number match except fc class match except loss-priority level Differentiated Services (DiffServ) code point. Where: value is the Differentiated services codepoint value (0..63). IP precedence value. Where: value is the IP Precedence codepoint value (0..7). IP protocol type. Values: tcp udp The IP source or destination address field. The UDP or TCP source or destination port field. The IP address of the source node sending the packet. The UDP or TCP source port field. The IP destination address field. The UDP or TCP destination port field. The forwarding class of the packet. The packet loss priority (PLP) level. Specify a single level or multiple levels: low medium-low medium-high high Epipe and VPLS filter conditions match except dot1p-user value User 802.1p VLAN Priority (0..7) match except dot1p-learned value match except dst-mac-addr address match except fc class Learned 802.1p VLAN Priority (0..7) Destination media access control (MAC) address of the packet. The forwarding class of the packet. 3HE AAAB-TQZZA 7

8 To configure a multi-vendor filter policy NFM-P Table 1 NFM-P Filter Policy supported conditions (continued) match except loss-priority level The packet loss priority (PLP) level. Specify a single level or multiple levels: low medium-low medium-high high 9 Click on the Filter Actions tab. Values of the string list (property genericne.filterterm.actionlist) are the supported actions performed as a result of classification and/or filtering: Table 2 NFM-P Filter Policy supported actions Action accept discard reject set dscp value set fc class-name set loss-priority level next Description Accept the packet. Discard a packet silently, without sending an Internet Control Message Protocol (ICMP) message. Reject the packet, with sending an Internet Control Message Protocol (ICMP) message. Note: Epipe and VPLS filters do not support reject action. Set Differentiated Services (DiffServ) code point. Classify packet to forwarding class. Set the packet loss priority (PLP) level to one of the following level values. low medium-low medium-high high Continue to next term in a filter. Note: These actions are supported by IPv4, IPv6, Epipe, and VPLS filter types. 10 If required, select a policer policy. 8 3HE AAAB-TQZZA

9 To configure a multi-vendor policer policy Configure actions for the filter policy. 1. Click Add in the Actions panel. The Entry Value form opens 2. Configure the Value parameter and click OK. Repeat this step to configure more actions, as required. If required, configure custom properties for the filter policy. 1. Click on the Custom Properties tab and click Add. The Entry Value form opens. 2. Configure the Key and Value parameters and click OK. Repeat this step to configure more custom properties, as required. Click OK to save the policy and close the form, or click Apply to save the policy. See the procedure To release and distribute a policy in the NSP NFM-P User Guide to distribute the policy to NEs. END OF STEPS 2 To configure a multi-vendor policer policy 2.1 Steps Choose Policies Multi-Vendor Policer from the NFM-P main menu. The Multi-Vendor Policer Policies form opens. Click Create or choose a multi-vendor policer policy and click Properties. The Multi-Vendor Policer Policy (Create Edit) form opens. Configure the parameters in the Identity panel and click Apply. Click on the Policer Rate tab and configure the parameters Configure actions for the policer policy. 1. Click on the Policer Actions tab and click Add. The Entry Value form opens. 2. Configure the Value parameter and click OK. Repeat this step to configure more actions, as required. 3HE AAAB-TQZZA 9

10 To configure a multi-vendor forwarding class policy NFM-P Values of the string list (property genericne.mvpolicerpolicy.actionlist) are the supported actions performed as a result of policing. Table 3 NFM-P Two-color Policer Policy supported actions Action discard set fc class-name set loss-priority level Description Discard a packet. Classify packet to forwarding class. Set the packet loss priority (PLP) level. low medium-low medium-high high 6 7 If required, configure custom properties. 1. Click on the Custom Properties tab and click Add. The Entry Value form opens. 2. Configure the Key and Value parameters and click OK. Repeat this step to configure more custom properties, as required. Click OK to save the policy and close the form, or click Apply to save the policy. See the procedure To release and distribute a policy in the NSP NFM-P User Guide to distribute the policy to NEs. END OF STEPS 3 To configure a multi-vendor forwarding class policy 3.1 Steps Choose Policies Multi-Vendor Forwarding Class from the NFM-P main menu. The Multi- Vendor Forwarding Class Policies form opens. Click Create or choose a multi-vendor forwarding class policy and click Properties. The Multi- Vendor Forwarding Class Policy (Create Edit) form opens. Configure the parameters in the Identity panel and click Apply. 10 3HE AAAB-TQZZA

11 To configure a multi-vendor class matching policy Click on the Queue tab and configure the Queue ID parameter. If required, configure custom properties. 1. Click on the Custom Properties tab and click Add. The Entry Value form opens. 2. Configure the Key and Value parameters and click OK. Click OK to save the policy and close the form, or click Apply to save the policy. See the procedure To release and distribute a policy in the NSP NFM-P User Guide to distribute the policy to NEs. END OF STEPS 4 To configure a multi-vendor class matching policy 4.1 Steps Choose Policies Multi-Vendor Class Matching from the NFM-P main menu. The Multi- Vendor Class Matching Policies form opens. Click Create or choose a multi-vendor class matching policy and click Properties. The Multi- Vendor Class Matching Policy (Create Edit) form opens. Configure the parameters in the Identity panel and click Apply. If required, configure conditions for the Class Matching policy. 1. Click on the Class Matching Conditions tab and configure the Condition Type parameter. 2. Click Add in the Conditions panel. The Entry Value form opens. 3. Configure the Value parameter and click OK. Repeat this step to configure more actions, as required. Values of the string list (property genericne.mvclassmatchingpolicy.conditionlist) are the supported conditions to perform packet classification. Table 4 NFM-P Class Matching Policy supported conditions Condition Description 3HE AAAB-TQZZA 11

12 To configure a multi-vendor class matching policy NFM-P Table 4 NFM-P Class Matching Policy supported conditions (continued) match except any match except acl policy-name match except class-match policy-name Any packets Where: policy-name is the name of referenced ACL Policy Where: policy-name is the name of referenced Class Matching Policy match except dot1p value IEEE 802.1p VLAN Priority (0..7) match except dscp value match except prec value Differentiated Services (DiffServ) code point Where: value is the Differentiated services codepoint value (0..63). IP precedence value Where: value is the IP Precedence codepoint value (0..7). match except lsp-exp value The MPLS Experimental value (0..7). match except src-mac-addr source MAC address match except dst-mac-addr destination MAC address Source MAC address Destination MAC address If required, configure custom properties. 1. Click on the Custom Properties tab and click Add. The Entry Value form opens. 2. Configure the Key and Value parameters and click OK. Repeat this step to configure more custom properties, as required. Click on the QoS Policy Class Terms tab. Click OK to save the policy and close the form, or click Apply to save the policy. See the procedure To release and distribute a policy in the NSP NFM-P User Guide to distribute the policy to NEs. END OF STEPS 12 3HE AAAB-TQZZA

13 To configure a multi-vendor QoS policy 5 To configure a multi-vendor QoS policy 5.1 Steps Choose Policies Multi-Vendor QoS from the NFM-P main menu. The Multi-Vendor QoS Policies form opens. Click Create or choose a multi-vendor QoS policy and click Properties. The Multi-Vendor QoS Policy (Create Edit) form opens. Configure the parameters in the Identity panel and click Apply. If required, configure custom properties. 1. Click on the Custom Properties tab and click Add. The Entry Value form opens. 2. Configure the Key and Value parameters and click OK. Repeat this step to configure more custom properties, as required. Click on the QoS Terms tab and click Create. The Multi-Vendor Policy Qos Term (Create) form opens. Select a Class Matching Policy and configure the required parameters. If you select the Policer or Shaper check box, the corresponding tab appears. To configure Policer attributes: 1. Click on the Policer tab and configure the attributes in the Attribute panel. 2. Click Add in the Actions panel. The Entry Value form opens. 3. Configure the Value parameter and click OK. Table 5 Action NFM-P supported QoS Policy Policer Term actions Description conform action exceed action Action when rate is less than conform burst. Action when rate is within conform and conform + exceed burst. 3HE AAAB-TQZZA 13

14 To configure a multi-vendor QoS policy NFM-P Table 5 NFM-P supported QoS Policy Policer Term actions (continued) violate action Action when rate is greater than conform + exceed burst. Where the value of action can be one of the following: transmit (accept) drop (discard) set param value The set action implies that the packet is transmitted. It means "set & transmit". See below for possible set actions. Set Action set dscp value set prec value Description Set Differentiated Services (DiffServ) code point. Where: value is the Differentiated services codepoint value (0..63). Set IP precedence value. Where: value is the IP Precedence codepoint value (0..7). set dot1p value Set the IEEE 802.1p VLAN Priority (0..7). set mpls-exp value Set the MPLS Experimental value (0..7) To configure Shaper attributes, click on the Shaper tab and configure the attributes. Configure custom properties for the Qos terms: 1. Click on the Custom Properties tab and click Add. The Entry Value form opens. 2. Configure the Key and Value parameters and click OK. Repeat this step to configure more custom properties, as required. If required, configure QoS actions. 1. Click on the QoS actions tab and click Add. The Entry Value form opens. 2. Configure the Value parameter and click OK. Repeat this step to configure more QoS actions, as required. Values of the string list (property genericne.qosterm.actionlist) are the supported actions after classification is applied. 14 3HE AAAB-TQZZA

15 To view multi-vendor generic policies Table 6 NFM-P supported QoS Policy Term actions Action set dscp value set prec value Description Set Differentiated Services (DiffServ) code point. Where: value is the Differentiated services codepoint value (0..63). Set IP precedence value. Where: value is the IP Precedence codepoint value (0..7). set dot1p value Set the IEEE 802.1p VLAN Priority (0..7). set mpls-exp value Set the MPLS Experimental value (0..7). 11 Click OK to save the policy and close the form, or click Apply to save the policy. See the procedure To release and distribute a policy in the NSP NFM-P User Guide to distribute the policy to NEs. END OF STEPS 6 To view multi-vendor generic policies 6.1 Purpose Use this procedure to view generic policies created on an NE. These policies typically apply to network elements produced by other vendors. 6.2 Steps Choose Policies Multi-Vendor Generic from the NFM-P main menu. The Multi-Vendor Generic Policies form opens. Choose Local or Global from the Policy scope drop-down menu. If you set it to Local, you must specify a Local Node IP Address by clicking Select and then choosing the required NE. Click OK. Click Search and choose a Multi-Vendor Generic policy. Click Properties. The selected multi-vendor generic policy form opens. 3HE AAAB-TQZZA 15

16 QoS Code Point Values NFM-P 5 View the policy properties, then click OK to close the form. END OF STEPS 7 QoS Code Point Values 7.1 Differentiated services code point values (DSCP) Some common values of the Differentiated services code point value (0..63). af11 (001010) af12 (001100) af13 (001110) af21 (010010) af22 (010100) af23 (010110) af31 (011010) af32 (011100) af33 (011110) af41 (100010) af42 (100100) af43 (100110) cs1 CS1(precedence 1) dscp (001000) cs2 CS2 precedence 2) dscp (010000) cs3 CS3(precedence 3) dscp (011000) cs4 CS4(precedence 4) dscp (100000) cs5 CS5(precedence 5) dscp (101000) cs6 CS6(precedence 6) dscp (110000) cs7 CS7(precedence 7) dscp (111000) be (000000) ef (101110) 7.2 IP Precedence code point values The IP Precedence code point values are from range (0..7). 5 (critical) 3 (flash) 4 (flash-override) 2 (immediate) 6 (internet, internetwork control precedence) 16 3HE AAAB-TQZZA

17 QoS Code Point Values 7 (network, network control) 1 (priority) 0 (routine) 7.3 IEEE 802.1p VLAN Priority code point (PCP) Priority code point (PCP) is a 3-bit field which refers to the IEEE 802.1p class of service and maps to the frame priority level. Values in order of lowest to highest priority are: 1 (BK, background) 0 (BE, best effort) 2 (EE, excellent effort) 3 (CA, critical application) 4 (VI, video) 5 (VO, voice) 6 (IC, internetwork control) 7 (NC, network control). 7.4 MPLS Experimental value Range: HE AAAB-TQZZA 17

18 QoS Code Point Values NFM-P 18 3HE AAAB-TQZZA